Another question I have is to please put an example of how it works to make it easier to review.

Good suggestion @FilledStacks !

All the commands except create app command loads the configuration file, stacked.json, from the root of the project unless you pass a custom configuration or a partial custom configuration through --config-path option.

Examples (current user location on terminal: my/path/to/my_project)

$> stacked create view settings

Will loads configuration from my/path/to/my_project/stacked.json

$> stacked create view settings --config-path=/Users/filledstacks/Desktop/dane.config.json

Will loads configuration from /Users/filledstacks/Desktop/dane.config.json

The create app command works different for obvious reason, as project does not exists there is no configuration inside to look for. When you create a project with stacked_cli you have 3 options.

Examples (current user location on terminal: my/path/to/my_project)

$> stacked create app my_app

• Global configuration, will loads configuration from /Users/filledstacks/.config/stacked/stacked.json.
• Default configuration, will loads default Stacked configuration, if there is no global configuration file on the location above.
• Next, will export configuration into stacked.json in the root of the project created.

$> stacked create app my_app --config-path=/Users/filledstacks/Desktop/dane.config.json

• Custom configuration, will loads configuration from the given location, /Users/filledstacks/Desktop/dane.config.json. Note, if configuration file is not found, will show an error for the user to correct the config-path option.
• Next, will export configuration into stacked.json in the root of the project created.

🎉 This PR is included in version 1.8.3 🎉

The release is available on:

• v1.8.3
• GitHub release

Your semantic-release bot 📦🚀